@copilot Figure out why updating TypeScript from 5.x to 6.x in this PR breaks the build and fix it.

@copilot Figure out why updating TypeScript from 5.x to 6.x in this PR breaks the build and fix it.

TypeScript 6 no longer auto-includes @types/jest global types, causing every test file to error with "Cannot find name 'beforeEach'/'test'/'expect'".

Fixed in commit 71a2c91 by:

1. Adding tsconfig.test.json — extends the main config but explicitly sets "types": ["jest", "node"] and scopes include to **/*.test.ts
2. Updating jest.config.js to pass tsconfig: "tsconfig.test.json" to ts-jest

The production build (tsc) is unaffected and all 58 tests now pass.

@copilot The build is still failing:

npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: ts-jest@29.4.6
npm error Found: typescript@6.0.2
npm error node_modules/typescript
npm error   dev typescript@"6.0.2" from the root project
npm error   peer typescript@"5.0.x || 5.1.x || 5.2.x || 5.3.x || 5.4.x || 5.5.x || 5.6.x || 5.7.x || 5.8.x || 5.9.x || 6.0.x" from typedoc@0.28.18
npm error   node_modules/typedoc
npm error     dev typedoc@"0.28.18" from the root project
npm error
npm error Could not resolve dependency:
npm error peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error node_modules/ts-jest
npm error   dev ts-jest@"29.4.6" from the root project
npm error
npm error Conflicting peer dependency: typescript@5.9.3
npm error node_modules/typescript
npm error   peer typescript@">=4.3 <6" from ts-jest@29.4.6
npm error   node_modules/ts-jest
npm error     dev ts-jest@"29.4.6" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.

@copilot The build is still failing:

...

Fixed in commit 45df436. ts-jest@29.4.6 had a peer dependency of typescript >=4.3 <6, so it rejected TypeScript 6. Updated to ts-jest@29.4.8, which expanded the range to >=4.3 <7. The npm install now resolves cleanly and all 58 tests pass.

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.